home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Tech Arsenal 1
/
Tech Arsenal (Arsenal Computer).ISO
/
tek-06
/
nwl200.zip
/
271.ASC
< prev
next >
Wrap
Text File
|
1991-10-29
|
2KB
|
41 lines
FYI
Note: The origin of this information may be internal or external to Novell. Novell makes
every effort within its means to verirfy this information. However, the information provided
in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied
claims to the validity of this information.
TITLE: Double Drive Mappings
DOCUMENT ID#: FYI.P.6039
DATE: October 29, 1991
PRODUCT: NetWare Lite
PRODUCT VERSION: All versions
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Double Drive Mappings
If you are using NetWare Lite on the same network with Native NetWare (NetWare 3.11 or
2.2) you may encounter the situation where NetWare Lite's Net utility reports a single drive
letter mapped to two different directories simultaneously (i.e. two F:'s). These "double drive
mappings" will occur in the following scenario:
Map a drive letter with NetWare Lite (e.g. net map f: cdrive server1).
Login to a NetWare 3.11 or 2.2 server. If your server's system login script has a
drive mapping that uses the same drive letter (f:) as the pervious NetWare Lite
mapping it will override the mapping without giving the usual NetWare warning
"drive already in use by local drive". Note: You will get the warning if you map
from the command line.
If you then return to NetWare Lite's Net utility, and select drive mappings, you
will see that f: appears as a NetWare Lite drive mapping and also as a Native
NetWare Mapping.
When this situation occurs the mapping to Native NetWare will be the active mapping.
NetWare Lite will flag its own mapping inactive and therefore inaccessible to the user. The
NetWare Lite mapping can not be deleted as long as it is inactive. To make the NetWare Lite
mapping active, delete the Native NetWare mapping.